Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a17485ba79c6c0ece05815833e735faaee9df7e2792f9579c24108fcdc26736

Tx prefix hash: c9911a7aea3e93720c9911c1b76af9f5378862eadfb02ddfdbc2205b748c9695
Tx public key: d415e405e24c9f63ecbb2f1281396a8d6e487a07c4f9752b9311a022b78169f8
Timestamp: 1724625044 Timestamp [UCT]: 2024-08-25 22:30:44 Age [y:d:h:m:s]: 00:224:06:02:34
Block: 1095899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160121 RingCT/type: yes/0
Extra: 01d415e405e24c9f63ecbb2f1281396a8d6e487a07c4f9752b9311a022b78169f802110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07ea2af8d0774566687fdf0e5acb9c3137fef5589294f3d660e181fa81c81694 0.600000000000 1571082 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": 1095909, "vin": [ { "gen": { "height": 1095899 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07ea2af8d0774566687fdf0e5acb9c3137fef5589294f3d660e181fa81c81694" } } ], "extra": [ 1, 212, 21, 228, 5, 226, 76, 159, 99, 236, 187, 47, 18, 129, 57, 106, 141, 110, 72, 122, 7, 196, 249, 117, 43, 147, 17, 160, 34, 183, 129, 105, 248, 2, 17, 0, 0, 0, 2, 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