Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f84e1dc2ef876af9a41726b8777a81a5bc20cdf334c11b81c886381f41d9974

Tx prefix hash: d559377f5c2f1adb62818318dadfbbdb4b75b26c79536e45e6a2ed1d9f2fafc3
Tx public key: 0a65ae2929a506aafacbdceda7329cdb728e2fc33e94a331d403b9235c86564c
Timestamp: 1724930201 Timestamp [UCT]: 2024-08-29 11:16:41 Age [y:d:h:m:s]: 00:258:06:29:09
Block: 1098427 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184482 RingCT/type: yes/0
Extra: 010a65ae2929a506aafacbdceda7329cdb728e2fc33e94a331d403b9235c86564c02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b9ba601957b01bada6a8407d2644284120b4fc845d822c753ff15d7d6a50c35 0.600000000000 1574140 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": 1098437, "vin": [ { "gen": { "height": 1098427 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b9ba601957b01bada6a8407d2644284120b4fc845d822c753ff15d7d6a50c35" } } ], "extra": [ 1, 10, 101, 174, 41, 41, 165, 6, 170, 250, 203, 220, 237, 167, 50, 156, 219, 114, 142, 47, 195, 62, 148, 163, 49, 212, 3, 185, 35, 92, 134, 86, 76, 2, 17, 0, 0, 0, 1, 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