Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 123c74a9fa25bdf7d052e5c343889591ccccb9752074b42458cee8e23ac3e6ec

Tx prefix hash: 13d48e81affbbc1f055cf54b5948b65e0937131c1f18b7ed7050c99de4031cc2
Tx public key: 406114b765e793a28ebba00b61d1e648ee2ec2b3481ecb2d40416176a06f93e4
Timestamp: 1581090601 Timestamp [UCT]: 2020-02-07 15:50:01 Age [y:d:h:m:s]: 04:324:19:28:37
Block: 60658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1123603 RingCT/type: yes/0
Extra: 01406114b765e793a28ebba00b61d1e648ee2ec2b3481ecb2d40416176a06f93e4021100000034c71d3ff9000000000000000000

1 output(s) for total of 386.380929604000 dcy

stealth address amount amount idx
00: 9e71ba35ceb481a211f96c61a9ffd149510d91ef7ef325c2e18f9f97e8a0f648 386.380929604000 111695 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": 60668, "vin": [ { "gen": { "height": 60658 } } ], "vout": [ { "amount": 386380929604, "target": { "key": "9e71ba35ceb481a211f96c61a9ffd149510d91ef7ef325c2e18f9f97e8a0f648" } } ], "extra": [ 1, 64, 97, 20, 183, 101, 231, 147, 162, 142, 187, 160, 11, 97, 209, 230, 72, 238, 46, 194, 179, 72, 30, 203, 45, 64, 65, 97, 118, 160, 111, 147, 228, 2, 17, 0, 0, 0, 52, 199, 29, 63, 249, 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