Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 662f830c70655d79133cf11c7cfb7853a83d1c4ecd3b0a7a0d7f4413d41c1386

Tx prefix hash: 902d2d83fe6944578b948c9b3f87f6edc7e4aa6719e4edd9250c3d86d0fad301
Tx public key: afc2f0c3bfe0950bff41f8a9fe3335e123aa4ec68ff112480b3434855601999c
Timestamp: 1717801632 Timestamp [UCT]: 2024-06-07 23:07:12 Age [y:d:h:m:s]: 01:008:17:40:54
Block: 1039332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267033 RingCT/type: yes/0
Extra: 01afc2f0c3bfe0950bff41f8a9fe3335e123aa4ec68ff112480b3434855601999c0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c4646620ca44b916fa6b03986de1cdbc0e46a4f20ef00e8a58378a47bca74d9 0.600000000000 1507967 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": 1039342, "vin": [ { "gen": { "height": 1039332 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c4646620ca44b916fa6b03986de1cdbc0e46a4f20ef00e8a58378a47bca74d9" } } ], "extra": [ 1, 175, 194, 240, 195, 191, 224, 149, 11, 255, 65, 248, 169, 254, 51, 53, 225, 35, 170, 78, 198, 143, 241, 18, 72, 11, 52, 52, 133, 86, 1, 153, 156, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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