Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c76b071a399c449a3c898277eb9b73b4ec904e3b7528ae350461184777258df7

Tx prefix hash: b5c64d4e35d3ac0a67e27408bfac50c92503d1d68ce68e8534fa063dea9d4a69
Tx public key: fe2c7f0a528c18cceedfc9486d6bbdb5bba2dcb701b714d33d0e75a68dd465e6
Timestamp: 1631566397 Timestamp [UCT]: 2021-09-13 20:53:17 Age [y:d:h:m:s]: 03:128:17:02:35
Block: 333164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 867581 RingCT/type: yes/0
Extra: 01fe2c7f0a528c18cceedfc9486d6bbdb5bba2dcb701b714d33d0e75a68dd465e602110000000120bdffe3000000000000000000

1 output(s) for total of 48.316710320000 dcy

stealth address amount amount idx
00: 2206e67db51aa00b00d3ea9ea42f6d2d5edd968d9ab4b4c0144b2cf5a9310c35 48.316710320000 687637 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": 333174, "vin": [ { "gen": { "height": 333164 } } ], "vout": [ { "amount": 48316710320, "target": { "key": "2206e67db51aa00b00d3ea9ea42f6d2d5edd968d9ab4b4c0144b2cf5a9310c35" } } ], "extra": [ 1, 254, 44, 127, 10, 82, 140, 24, 204, 238, 223, 201, 72, 109, 107, 189, 181, 187, 162, 220, 183, 1, 183, 20, 211, 61, 14, 117, 166, 141, 212, 101, 230, 2, 17, 0, 0, 0, 1, 32, 189, 255, 227, 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