Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2faa2f1b8da45ad26d1c38a5837aa63c6a7937e95710a429898ed3704b31f170

Tx prefix hash: 4f8ae7a5a19fc2c0d012b96de9732a88ea366c6185bd0978551043af97a28047
Tx public key: 5911c8be1ee9a87c5216ea2d3c35d8d79bbf5f64c534f984d97d4415d98889b7
Timestamp: 1711788887 Timestamp [UCT]: 2024-03-30 08:54:47 Age [y:d:h:m:s]: 01:006:23:42:22
Block: 989507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265932 RingCT/type: yes/0
Extra: 015911c8be1ee9a87c5216ea2d3c35d8d79bbf5f64c534f984d97d4415d98889b70211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02317eac7561173fa2d679f820c96861618db5698260e0e594159f507cf59e76 0.600000000000 1449806 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": 989517, "vin": [ { "gen": { "height": 989507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02317eac7561173fa2d679f820c96861618db5698260e0e594159f507cf59e76" } } ], "extra": [ 1, 89, 17, 200, 190, 30, 233, 168, 124, 82, 22, 234, 45, 60, 53, 216, 215, 155, 191, 95, 100, 197, 52, 249, 132, 217, 125, 68, 21, 217, 136, 137, 183, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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