Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 232fb083d7a1c96b7a37552c7300e0fefe16ed7cf90de9f824a0f7a311b79f7a

Tx prefix hash: 1c0e6b2e8e6628607ca6403ebcfbe14c1c85fce20df9aa98921bf5011c0b4a2c
Tx public key: 0699f41a865c2ce5c024f3629e6bf9f0d11a08c2c0cf31445baaf6f5b935733a
Timestamp: 1729007631 Timestamp [UCT]: 2024-10-15 15:53:51 Age [y:d:h:m:s]: 00:185:12:27:10
Block: 1132241 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132370 RingCT/type: yes/0
Extra: 010699f41a865c2ce5c024f3629e6bf9f0d11a08c2c0cf31445baaf6f5b935733a02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 88f2cf5a73f4386cf64045e92dc03ec24ff862f9050259efcd47b929cafa7b09 0.600000000000 1615154 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": 1132251, "vin": [ { "gen": { "height": 1132241 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88f2cf5a73f4386cf64045e92dc03ec24ff862f9050259efcd47b929cafa7b09" } } ], "extra": [ 1, 6, 153, 244, 26, 134, 92, 44, 229, 192, 36, 243, 98, 158, 107, 249, 240, 209, 26, 8, 194, 192, 207, 49, 68, 91, 170, 246, 245, 185, 53, 115, 58, 2, 17, 0, 0, 0, 3, 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