Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c64b5fff72aa123b48ab79a39d6213a06c4399fcbc2f3b7fe9d93556c57f2c0

Tx prefix hash: 38794b798dd7693faec79e172a19ae87e7e187f02e9cb02fadad5e02ec15b2b9
Tx public key: ea487ca1fe9de26a8bd7e5633458f7ad3cc9f89c4a25cea9209f93a9a43aafd6
Timestamp: 1734622915 Timestamp [UCT]: 2024-12-19 15:41:55 Age [y:d:h:m:s]: 00:095:17:41:25
Block: 1178703 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68174 RingCT/type: yes/0
Extra: 01ea487ca1fe9de26a8bd7e5633458f7ad3cc9f89c4a25cea9209f93a9a43aafd602110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d950a2add9865ff47a5cc09086fb3f99d9182234fec352993617db64297c733 0.600000000000 1665092 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": 1178713, "vin": [ { "gen": { "height": 1178703 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d950a2add9865ff47a5cc09086fb3f99d9182234fec352993617db64297c733" } } ], "extra": [ 1, 234, 72, 124, 161, 254, 157, 226, 106, 139, 215, 229, 99, 52, 88, 247, 173, 60, 201, 248, 156, 74, 37, 206, 169, 32, 159, 147, 169, 164, 58, 175, 214, 2, 17, 0, 0, 0, 12, 0, 127, 151, 138, 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