Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f075d2c9d0ed1080d37ed90f1f85468dc0144a105e5cafa386020cfd0dc5af9

Tx prefix hash: e5db8e60fff046461799b3ea8b87ff25166fcb520189707871ee2790a5103213
Tx public key: 457786893b334072f779ddc9f36806382c061ceb6ae0449c88a260f582d1d6fc
Timestamp: 1578785455 Timestamp [UCT]: 2020-01-11 23:30:55 Age [y:d:h:m:s]: 05:029:22:13:30
Block: 43508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1171557 RingCT/type: yes/0
Extra: 01457786893b334072f779ddc9f36806382c061ceb6ae0449c88a260f582d1d6fc02110000000b8a2ee0d9000000000000000000

1 output(s) for total of 440.393375372000 dcy

stealth address amount amount idx
00: 896754bf42498d8e34ec2ebf4a4c3f54719679bb2e47af9a69a4ea104db5c61e 440.393375372000 78839 of 0

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": 43518, "vin": [ { "gen": { "height": 43508 } } ], "vout": [ { "amount": 440393375372, "target": { "key": "896754bf42498d8e34ec2ebf4a4c3f54719679bb2e47af9a69a4ea104db5c61e" } } ], "extra": [ 1, 69, 119, 134, 137, 59, 51, 64, 114, 247, 121, 221, 201, 243, 104, 6, 56, 44, 6, 28, 235, 106, 224, 68, 156, 136, 162, 96, 245, 130, 209, 214, 252, 2, 17, 0, 0, 0, 11, 138, 46, 224, 217, 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