Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75e0b35dbbb0f5988f2108f989f6a7eaddf64630dc4e063d5e22ddf3f70afc28

Tx prefix hash: 0f0437bf5bafbab1dad2440e3e924732412fd1ff224294599090edde173ff341
Tx public key: 7dba74fd5cc59cf7589718774d8a6c7d0ea0137ebcc8121b5f9a237a8215d05d
Timestamp: 1736884038 Timestamp [UCT]: 2025-01-14 19:47:18 Age [y:d:h:m:s]: 00:307:11:44:50
Block: 1197376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217283 RingCT/type: yes/0
Extra: 017dba74fd5cc59cf7589718774d8a6c7d0ea0137ebcc8121b5f9a237a8215d05d0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dfd380c6616af0177bc87f317f63cd581c048e9e737e68214f94b133bbbf984c 0.600000000000 1683983 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": 1197386, "vin": [ { "gen": { "height": 1197376 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dfd380c6616af0177bc87f317f63cd581c048e9e737e68214f94b133bbbf984c" } } ], "extra": [ 1, 125, 186, 116, 253, 92, 197, 156, 247, 88, 151, 24, 119, 77, 138, 108, 125, 14, 160, 19, 126, 188, 200, 18, 27, 95, 154, 35, 122, 130, 21, 208, 93, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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