Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7963762e6ee91c1f9fac89b33e7ee608ab89a672eb8b1726bb99ef27b407d7a1

Tx prefix hash: f8cff440a8ac1a5e02566b2036c7a5cfddb14487e03ca9b380dd9b8e07371c24
Tx public key: 4a1b8954f10fba522bb1a9eb1fdbb541c63f80786d65c0f89672d5a68bf37a53
Timestamp: 1735348111 Timestamp [UCT]: 2024-12-28 01:08:31 Age [y:d:h:m:s]: 00:169:19:29:17
Block: 1184658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121118 RingCT/type: yes/0
Extra: 014a1b8954f10fba522bb1a9eb1fdbb541c63f80786d65c0f89672d5a68bf37a53021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8fe4fa15e905ab73583538d285ce51a38703395bca9d0ea5c0f5acd618aacbc0 0.600000000000 1671117 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": 1184668, "vin": [ { "gen": { "height": 1184658 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8fe4fa15e905ab73583538d285ce51a38703395bca9d0ea5c0f5acd618aacbc0" } } ], "extra": [ 1, 74, 27, 137, 84, 241, 15, 186, 82, 43, 177, 169, 235, 31, 219, 181, 65, 198, 63, 128, 120, 109, 101, 192, 248, 150, 114, 213, 166, 139, 243, 122, 83, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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