Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 988d014039a0b3ce9d30da01cba3033d9ebaf78bfc9780e444201d7eb2547d34

Tx prefix hash: dcfd0fed6cf7a329ceff195ab5c100e46ac754913359c4e5e70df6b487c714e2
Tx public key: c54e5e336fa914133809279f7514b94c379abbc3ad97ea2caa215d0e4ee1ee51
Timestamp: 1652810154 Timestamp [UCT]: 2022-05-17 17:55:54 Age [y:d:h:m:s]: 02:304:03:35:47
Block: 503040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 737784 RingCT/type: yes/0
Extra: 01c54e5e336fa914133809279f7514b94c379abbc3ad97ea2caa215d0e4ee1ee5102110000000275e3f0e9000000000000000000

1 output(s) for total of 13.220167023000 dcy

stealth address amount amount idx
00: 91fbc66457af4dd421f4d76668800e01a275d6dee034efb01fa7de0576d5a3a1 13.220167023000 928043 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": 503050, "vin": [ { "gen": { "height": 503040 } } ], "vout": [ { "amount": 13220167023, "target": { "key": "91fbc66457af4dd421f4d76668800e01a275d6dee034efb01fa7de0576d5a3a1" } } ], "extra": [ 1, 197, 78, 94, 51, 111, 169, 20, 19, 56, 9, 39, 159, 117, 20, 185, 76, 55, 154, 187, 195, 173, 151, 234, 44, 170, 33, 93, 14, 78, 225, 238, 81, 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