Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6305e039ca46e515bcf3fb4385a32b354ce003a0326133867e745f8814b79ae9

Tx prefix hash: 2c78e8d0e4040778eb629efb5188f1e4c80f7636b94b1e695850da7235c2e063
Tx public key: b1dc745170572ebad11c1aade94c305e3fd5ba86fbbeb52539ceb19a3505c2d1
Timestamp: 1579273412 Timestamp [UCT]: 2020-01-17 15:03:32 Age [y:d:h:m:s]: 04:243:14:46:59
Block: 47746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1063409 RingCT/type: yes/0
Extra: 01b1dc745170572ebad11c1aade94c305e3fd5ba86fbbeb52539ceb19a3505c2d1021100000048391a8d0e000000000000000000

1 output(s) for total of 426.381661877000 dcy

stealth address amount amount idx
00: 7043858af4767e3ee50cf266164118dfd6e2f6bf6c6c4a4192017a30e7e3ba57 426.381661877000 88169 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": 47756, "vin": [ { "gen": { "height": 47746 } } ], "vout": [ { "amount": 426381661877, "target": { "key": "7043858af4767e3ee50cf266164118dfd6e2f6bf6c6c4a4192017a30e7e3ba57" } } ], "extra": [ 1, 177, 220, 116, 81, 112, 87, 46, 186, 209, 28, 26, 173, 233, 76, 48, 94, 63, 213, 186, 134, 251, 190, 181, 37, 57, 206, 177, 154, 53, 5, 194, 209, 2, 17, 0, 0, 0, 72, 57, 26, 141, 14, 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