Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eda40f619cd63994e0f0610c63363415196d49e46154e1bbbc9a7c4f05acd5c6

Tx prefix hash: cfbdcaf20c9a24361e408ba40d3c8b497cee5f047373344d5e19a8361741c4eb
Tx public key: 17049b7f87cc86802ce7089bc38f6c2907fbb9e15f71dc8f8d1fd50b37578e05
Timestamp: 1724918980 Timestamp [UCT]: 2024-08-29 08:09:40 Age [y:d:h:m:s]: 00:268:03:26:33
Block: 1098334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191534 RingCT/type: yes/0
Extra: 0117049b7f87cc86802ce7089bc38f6c2907fbb9e15f71dc8f8d1fd50b37578e0502110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7dfbbe26e6bdcb6def617f3f2aabd937147ac6bb0438dc6ea4d007fa18c407bd 0.600000000000 1574015 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": 1098344, "vin": [ { "gen": { "height": 1098334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7dfbbe26e6bdcb6def617f3f2aabd937147ac6bb0438dc6ea4d007fa18c407bd" } } ], "extra": [ 1, 23, 4, 155, 127, 135, 204, 134, 128, 44, 231, 8, 155, 195, 143, 108, 41, 7, 251, 185, 225, 95, 113, 220, 143, 141, 31, 213, 11, 55, 87, 142, 5, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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