Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 627ae026dd6fbce8e1750501aa4d1944ff5dbd626ee9fd1f3b711d7705fd98f3

Tx prefix hash: b8215a8c2e5c133624918e3e8b696487c6b4d96cea70e2a2fd297e1ac761e446
Tx public key: 8b7fdcb61cf21988744f788a0f53cd69186d9e99252c127bebd219a43c59cfec
Timestamp: 1736491447 Timestamp [UCT]: 2025-01-10 06:44:07 Age [y:d:h:m:s]: 00:085:05:36:18
Block: 1194143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60702 RingCT/type: yes/0
Extra: 018b7fdcb61cf21988744f788a0f53cd69186d9e99252c127bebd219a43c59cfec0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73e9087baec705486bece9df7cb5a6e1351ffcf07bc48551f540c489db6ee76d 0.600000000000 1680710 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": 1194153, "vin": [ { "gen": { "height": 1194143 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73e9087baec705486bece9df7cb5a6e1351ffcf07bc48551f540c489db6ee76d" } } ], "extra": [ 1, 139, 127, 220, 182, 28, 242, 25, 136, 116, 79, 120, 138, 15, 83, 205, 105, 24, 109, 158, 153, 37, 44, 18, 123, 235, 210, 25, 164, 60, 89, 207, 236, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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