Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eafc3458d10fcecc4258be11aab6eaa09834d5668b972dc2fa86c894eea90d8d

Tx prefix hash: 0c25bf67592291a599a2c331327c8a42f73c7b85e5ab62baea5b1eff34a692a1
Tx public key: 00f63a15732f62e7918f31e16160d3f8f866b3451479653708036cc4e2d315ed
Timestamp: 1714951488 Timestamp [UCT]: 2024-05-05 23:24:48 Age [y:d:h:m:s]: 01:184:02:43:01
Block: 1015701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390187 RingCT/type: yes/0
Extra: 0100f63a15732f62e7918f31e16160d3f8f866b3451479653708036cc4e2d315ed0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e43431d31e9cae63fea68e51d8c1777bab03df493178f282c0c0d5aa1c6e9efc 0.600000000000 1479140 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": 1015711, "vin": [ { "gen": { "height": 1015701 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e43431d31e9cae63fea68e51d8c1777bab03df493178f282c0c0d5aa1c6e9efc" } } ], "extra": [ 1, 0, 246, 58, 21, 115, 47, 98, 231, 145, 143, 49, 225, 97, 96, 211, 248, 248, 102, 179, 69, 20, 121, 101, 55, 8, 3, 108, 196, 226, 211, 21, 237, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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