Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 572f87d1ee20119c9d72a1d0d1549cb284225e533c24c77108effbc23a30bb19

Tx prefix hash: 4ee3b71329baea3260f21fdf0ed811f1a79bde3717f22d4edce1ebc10c83e505
Tx public key: bc12f49503ddea26ff57d2ad5109bf3335d95376ab1556647c7d5c48bfa2e2c8
Timestamp: 1737954659 Timestamp [UCT]: 2025-01-27 05:10:59 Age [y:d:h:m:s]: 00:141:19:39:17
Block: 1206010 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101292 RingCT/type: yes/0
Extra: 01bc12f49503ddea26ff57d2ad5109bf3335d95376ab1556647c7d5c48bfa2e2c80211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f05f13c437b2e16db4436106734d9c30e29e5b7bb862f58ce0bf7809e03aeab 0.600000000000 1692711 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": 1206020, "vin": [ { "gen": { "height": 1206010 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f05f13c437b2e16db4436106734d9c30e29e5b7bb862f58ce0bf7809e03aeab" } } ], "extra": [ 1, 188, 18, 244, 149, 3, 221, 234, 38, 255, 87, 210, 173, 81, 9, 191, 51, 53, 217, 83, 118, 171, 21, 86, 100, 124, 125, 92, 72, 191, 162, 226, 200, 2, 17, 0, 0, 0, 2, 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