Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c394c1fe2bbd553bf5030ec9c4cce873a8133c3cbce557e1404c7c8e9c0acd4c

Tx prefix hash: ed1e3cb6d666faf63f869500d6372404aed8aad08379b2f1ff8c7bec3b95a610
Tx public key: fcd0bc2043b9abef4857e451329ecd31ae07d71d2478308d4bf9cfb67839e64a
Timestamp: 1711662521 Timestamp [UCT]: 2024-03-28 21:48:41 Age [y:d:h:m:s]: 00:362:04:54:44
Block: 988452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258931 RingCT/type: yes/0
Extra: 01fcd0bc2043b9abef4857e451329ecd31ae07d71d2478308d4bf9cfb67839e64a02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6eede7025d4333be710d3f4c6194d14da98b31c4f5986f439db55fa1b412c02b 0.600000000000 1448731 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": 988462, "vin": [ { "gen": { "height": 988452 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6eede7025d4333be710d3f4c6194d14da98b31c4f5986f439db55fa1b412c02b" } } ], "extra": [ 1, 252, 208, 188, 32, 67, 185, 171, 239, 72, 87, 228, 81, 50, 158, 205, 49, 174, 7, 215, 29, 36, 120, 48, 141, 75, 249, 207, 182, 120, 57, 230, 74, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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