Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf20a7e1ef9e954184bbe3369d086e2f0f6765252c6da8bf7d1aaa3c597f5839

Tx prefix hash: 99b3abfecda964ee914e23933eb5da2f5dcacaec5905c4f00cd806c8b820fd00
Tx public key: ebdd39d2268a708ea914f342f013a0e014bce941d15aa9e5867a881192518c66
Timestamp: 1728537411 Timestamp [UCT]: 2024-10-10 05:16:51 Age [y:d:h:m:s]: 00:167:09:23:15
Block: 1128331 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119407 RingCT/type: yes/0
Extra: 01ebdd39d2268a708ea914f342f013a0e014bce941d15aa9e5867a881192518c6602110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e98280a326fe814aad492fdb321d93acf595aaf69d01aeb913c4762ab1e3909a 0.600000000000 1611148 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": 1128341, "vin": [ { "gen": { "height": 1128331 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e98280a326fe814aad492fdb321d93acf595aaf69d01aeb913c4762ab1e3909a" } } ], "extra": [ 1, 235, 221, 57, 210, 38, 138, 112, 142, 169, 20, 243, 66, 240, 19, 160, 224, 20, 188, 233, 65, 209, 90, 169, 229, 134, 122, 136, 17, 146, 81, 140, 102, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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