Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f20c64e0dee10d98d0223b3303fa12e4efd04434ff28c1aa606b52987d0cbb1b

Tx prefix hash: 64bc5da23aacd94f09feeaacdd376de1914fa312f1461f209cae6ee58b31ff20
Tx public key: cc2b6c5add942cf8ceedc60f58e2d46de880767be38183d3c102d5a75e812336
Timestamp: 1578514046 Timestamp [UCT]: 2020-01-08 20:07:26 Age [y:d:h:m:s]: 05:056:22:07:01
Block: 41589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1190538 RingCT/type: yes/0
Extra: 01cc2b6c5add942cf8ceedc60f58e2d46de880767be38183d3c102d5a75e81233602110000000117786bcf000000000000000000

1 output(s) for total of 446.888546303000 dcy

stealth address amount amount idx
00: 1b6f3ed3cb998267e202e3e63c4504049b3987717e54bc89f83bd9fc44dd61a1 446.888546303000 74198 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": 41599, "vin": [ { "gen": { "height": 41589 } } ], "vout": [ { "amount": 446888546303, "target": { "key": "1b6f3ed3cb998267e202e3e63c4504049b3987717e54bc89f83bd9fc44dd61a1" } } ], "extra": [ 1, 204, 43, 108, 90, 221, 148, 44, 248, 206, 237, 198, 15, 88, 226, 212, 109, 232, 128, 118, 123, 227, 129, 131, 211, 193, 2, 213, 167, 94, 129, 35, 54, 2, 17, 0, 0, 0, 1, 23, 120, 107, 207, 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