Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 544e4f9b9b7e83fda4dc7f110b401a142da13f5c8a615f62109140c41ea11242

Tx prefix hash: 3662499489015e993eb9472598a38930b507328685442440fd42741602b15c61
Tx public key: b591f4377ed04c13d9ce02a39a24e1bcb149e32737aa1a31c52d6ad37ee4e4d9
Timestamp: 1717633050 Timestamp [UCT]: 2024-06-06 00:17:30 Age [y:d:h:m:s]: 01:161:23:48:12
Block: 1037934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374355 RingCT/type: yes/0
Extra: 01b591f4377ed04c13d9ce02a39a24e1bcb149e32737aa1a31c52d6ad37ee4e4d902110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 122e8ca2c2d3721e3eb38b5a88f3946efa0b72bf4d470a25c600bf9d57f1d298 0.600000000000 1506491 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1037944, "vin": [ { "gen": { "height": 1037934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "122e8ca2c2d3721e3eb38b5a88f3946efa0b72bf4d470a25c600bf9d57f1d298" } } ], "extra": [ 1, 181, 145, 244, 55, 126, 208, 76, 19, 217, 206, 2, 163, 154, 36, 225, 188, 177, 73, 227, 39, 55, 170, 26, 49, 197, 45, 106, 211, 126, 228, 228, 217, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8