Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c8c471ca4aefe7613190d0a7153852ded0cce0c37a49749f1b7c39e577329a9

Tx prefix hash: bd83fc5b385c3ee67686ca688de5d5e7fb47691585e77095dcc15d5bb9281a75
Tx public key: 04bac021461d75ea40809e4a8bb3e30a5fbe1d34b0e9e266ff8b49f2932d4c0e
Timestamp: 1663409549 Timestamp [UCT]: 2022-09-17 10:12:29 Age [y:d:h:m:s]: 02:149:05:23:27
Block: 589820 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 627931 RingCT/type: yes/0
Extra: 0104bac021461d75ea40809e4a8bb3e30a5fbe1d34b0e9e266ff8b49f2932d4c0e02110000000275e3f0e9000000000000000000

1 output(s) for total of 6.818385766000 dcy

stealth address amount amount idx
00: f07450f77fefd642d77dfff89958167d28da4167d13cd2c1e12f5d5d3c79bfee 6.818385766000 1024167 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": 589830, "vin": [ { "gen": { "height": 589820 } } ], "vout": [ { "amount": 6818385766, "target": { "key": "f07450f77fefd642d77dfff89958167d28da4167d13cd2c1e12f5d5d3c79bfee" } } ], "extra": [ 1, 4, 186, 192, 33, 70, 29, 117, 234, 64, 128, 158, 74, 139, 179, 227, 10, 95, 190, 29, 52, 176, 233, 226, 102, 255, 139, 73, 242, 147, 45, 76, 14, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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