Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ac45e7c40e3ae89951248e2bf9e9926bf93e2fdfaacb3a277e5dd64d8d4dc12

Tx prefix hash: 54c495aca96002ae28192337ff36e6c6aa53633f38f708fc2dad9a1303185886
Tx public key: b2869f10a9c7738001a1ab1f7a83804e3621575f06bae81068bcae81da048571
Timestamp: 1717991677 Timestamp [UCT]: 2024-06-10 03:54:37 Age [y:d:h:m:s]: 00:298:18:16:39
Block: 1040911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213500 RingCT/type: yes/0
Extra: 01b2869f10a9c7738001a1ab1f7a83804e3621575f06bae81068bcae81da04857102110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e926052b92ad2fd1daed301f9832d1fd8a22d6e24e2de5f9ffb50abfd61767d 0.600000000000 1509574 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": 1040921, "vin": [ { "gen": { "height": 1040911 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e926052b92ad2fd1daed301f9832d1fd8a22d6e24e2de5f9ffb50abfd61767d" } } ], "extra": [ 1, 178, 134, 159, 16, 169, 199, 115, 128, 1, 161, 171, 31, 122, 131, 128, 78, 54, 33, 87, 95, 6, 186, 232, 16, 104, 188, 174, 129, 218, 4, 133, 113, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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