Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c9d3c1df6a10247b9ecbe3c0cfb60630d1a60c037748be999bc33df2498e28d

Tx prefix hash: a6ec6c9e712ca3ef432896fdb64c1c23ff80df4724991a037e6bd348c4fabf60
Tx public key: ae857fa4a1ae0a7f993e6854f03878521c95989fff70b766b1a75d2b9d018d3a
Timestamp: 1663930754 Timestamp [UCT]: 2022-09-23 10:59:14 Age [y:d:h:m:s]: 02:100:18:54:42
Block: 594040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 593625 RingCT/type: yes/0
Extra: 01ae857fa4a1ae0a7f993e6854f03878521c95989fff70b766b1a75d2b9d018d3a021100000001faf35c9c000000000000000000

1 output(s) for total of 6.602356197000 dcy

stealth address amount amount idx
00: 70f0d95a91933949fb211f07362628912bbe5e357e2939bcadfe6af2d96a86aa 6.602356197000 1028881 of 0

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": 594050, "vin": [ { "gen": { "height": 594040 } } ], "vout": [ { "amount": 6602356197, "target": { "key": "70f0d95a91933949fb211f07362628912bbe5e357e2939bcadfe6af2d96a86aa" } } ], "extra": [ 1, 174, 133, 127, 164, 161, 174, 10, 127, 153, 62, 104, 84, 240, 56, 120, 82, 28, 149, 152, 159, 255, 112, 183, 102, 177, 167, 93, 43, 157, 1, 141, 58, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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