Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6acd2a8c2f07a6ba8903612fb0466313cb46309bbc626b754e95e9742460e2a

Tx prefix hash: c8f37a2dad138e0609708618aac0cc0462c66ae2a13b4aab9d8d1e262c1af3f8
Tx public key: 9e1b2bc3c31d060e2fdda1db4b5eac9f5dd8ff8059f817e0c1dea933f07a0e5d
Timestamp: 1723794363 Timestamp [UCT]: 2024-08-16 07:46:03 Age [y:d:h:m:s]: 00:243:22:18:30
Block: 1089013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174220 RingCT/type: yes/0
Extra: 019e1b2bc3c31d060e2fdda1db4b5eac9f5dd8ff8059f817e0c1dea933f07a0e5d02110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca64a2d6957b1506186cde28d90db8564910274509c6bc4b78d3209dc8444599 0.600000000000 1563632 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": 1089023, "vin": [ { "gen": { "height": 1089013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca64a2d6957b1506186cde28d90db8564910274509c6bc4b78d3209dc8444599" } } ], "extra": [ 1, 158, 27, 43, 195, 195, 29, 6, 14, 47, 221, 161, 219, 75, 94, 172, 159, 93, 216, 255, 128, 89, 248, 23, 224, 193, 222, 169, 51, 240, 122, 14, 93, 2, 17, 0, 0, 0, 12, 233, 20, 221, 21, 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