Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17fbb827f650efc87d3d288d6b20901e354552ff83fa0f5d254458ea025c546d

Tx prefix hash: e578ba206eafc07b29850f3ee323125ba803c26558a804fd79126c5e364a126f
Tx public key: 2352a4a09d3412ec326631a648dcdf7a1bc55fe05ae550e2f9f2953c3b51e0ef
Timestamp: 1648256245 Timestamp [UCT]: 2022-03-26 00:57:25 Age [y:d:h:m:s]: 02:287:10:30:07
Block: 466460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 724972 RingCT/type: yes/0
Extra: 012352a4a09d3412ec326631a648dcdf7a1bc55fe05ae550e2f9f2953c3b51e0ef02110000000606faf294000000000000000000

1 output(s) for total of 17.475299913000 dcy

stealth address amount amount idx
00: facb56fe3977572bcea2a005e106ab4ca8a410e86060259d5b620166f3754ab2 17.475299913000 884779 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": 466470, "vin": [ { "gen": { "height": 466460 } } ], "vout": [ { "amount": 17475299913, "target": { "key": "facb56fe3977572bcea2a005e106ab4ca8a410e86060259d5b620166f3754ab2" } } ], "extra": [ 1, 35, 82, 164, 160, 157, 52, 18, 236, 50, 102, 49, 166, 72, 220, 223, 122, 27, 197, 95, 224, 90, 229, 80, 226, 249, 242, 149, 60, 59, 81, 224, 239, 2, 17, 0, 0, 0, 6, 6, 250, 242, 148, 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