Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd2264d27b335643a57db770029d0de939dec05a3f33ec6dfc2115df6a8634f9

Tx prefix hash: f68a560c992a77b8327df9ae4d13d24ec094b6b973d7c46f243c35b5ac1a1dfc
Tx public key: 67a719c0c44a686748abb151c4926e4e91ef78534cc134e2727fa1086547a05a
Timestamp: 1702412017 Timestamp [UCT]: 2023-12-12 20:13:37 Age [y:d:h:m:s]: 01:163:18:31:42
Block: 911758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378213 RingCT/type: yes/0
Extra: 0167a719c0c44a686748abb151c4926e4e91ef78534cc134e2727fa1086547a05a021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fffc6e66c883a167316b3db1b0677dc30f332b3fdb0c17b0331d6e2497dee1dc 0.600000000000 1368974 of 15

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": 911768, "vin": [ { "gen": { "height": 911758 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fffc6e66c883a167316b3db1b0677dc30f332b3fdb0c17b0331d6e2497dee1dc" } } ], "extra": [ 1, 103, 167, 25, 192, 196, 74, 104, 103, 72, 171, 177, 81, 196, 146, 110, 78, 145, 239, 120, 83, 76, 193, 52, 226, 114, 127, 161, 8, 101, 71, 160, 90, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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