Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f281fb4915138b7258b05f8cdfe39bd76648312e4a05116184a7ebf01954ec2

Tx prefix hash: 2265d87af8ff2bb48f67c80152f8fa9f8edf73ee611378a53b6508c58511214a
Tx public key: bffc6a25e5f0bf21a669c44323b9c4621b02685c99d13ce1aa5a5d0228ae1466
Timestamp: 1702897345 Timestamp [UCT]: 2023-12-18 11:02:25 Age [y:d:h:m:s]: 01:327:11:02:02
Block: 915764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492893 RingCT/type: yes/0
Extra: 01bffc6a25e5f0bf21a669c44323b9c4621b02685c99d13ce1aa5a5d0228ae1466021100000009faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80c1845e4f233b39335c35251fbfea6298ea155471d08f019414dc3f2afa7ed7 0.600000000000 1373188 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": 915774, "vin": [ { "gen": { "height": 915764 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80c1845e4f233b39335c35251fbfea6298ea155471d08f019414dc3f2afa7ed7" } } ], "extra": [ 1, 191, 252, 106, 37, 229, 240, 191, 33, 166, 105, 196, 67, 35, 185, 196, 98, 27, 2, 104, 92, 153, 209, 60, 225, 170, 90, 93, 2, 40, 174, 20, 102, 2, 17, 0, 0, 0, 9, 250, 243, 92, 156, 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