Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00e1504fb68ad1cc537aca653df981e9c3a0a34e3d8c03c5bd5ff150df3852d2

Tx prefix hash: 586f7276afeee8e8e7efbd1cf8e2b1fd62d21a213f37c6c0474b7a2f17492f11
Tx public key: b40a7fc79f1ba831bd88859ab4dd534b18afd0a059ffce31cbadd0d21f98355f
Timestamp: 1697051117 Timestamp [UCT]: 2023-10-11 19:05:17 Age [y:d:h:m:s]: 02:027:11:38:19
Block: 867502 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 539253 RingCT/type: yes/0
Extra: 01b40a7fc79f1ba831bd88859ab4dd534b18afd0a059ffce31cbadd0d21f98355f02110000000675e3f0e9000000000000000000

1 output(s) for total of 0.819607243000 dcy

stealth address amount amount idx
00: 1c034d71bcae6c433b96d9de8081b6258e8c610ab55b75291aeefa3095ad313f 0.819607243000 1322190 of 0

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": 867512, "vin": [ { "gen": { "height": 867502 } } ], "vout": [ { "amount": 819607243, "target": { "key": "1c034d71bcae6c433b96d9de8081b6258e8c610ab55b75291aeefa3095ad313f" } } ], "extra": [ 1, 180, 10, 127, 199, 159, 27, 168, 49, 189, 136, 133, 154, 180, 221, 83, 75, 24, 175, 208, 160, 89, 255, 206, 49, 203, 173, 208, 210, 31, 152, 53, 95, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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