Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99c6cbd2845a08b9db912469a73acc6e309e7119fa284d57569f3c1eff480e03

Tx prefix hash: f80005112d0dbd69b8656b3d5840ab77d3ac1bd4e55c34de6e2790dd5c4c0b62
Tx public key: b1f9fd1449f60ee666cd3aa901cf028b47a1d93520abda7b4b173219e63047fc
Timestamp: 1711863522 Timestamp [UCT]: 2024-03-31 05:38:42 Age [y:d:h:m:s]: 01:003:08:42:52
Block: 990120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263341 RingCT/type: yes/0
Extra: 01b1f9fd1449f60ee666cd3aa901cf028b47a1d93520abda7b4b173219e63047fc0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b66c37e47133a306d3856407b5528d46210b9d46b479c004ecbecb0a87f6916 0.600000000000 1450442 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": 990130, "vin": [ { "gen": { "height": 990120 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b66c37e47133a306d3856407b5528d46210b9d46b479c004ecbecb0a87f6916" } } ], "extra": [ 1, 177, 249, 253, 20, 73, 246, 14, 230, 102, 205, 58, 169, 1, 207, 2, 139, 71, 161, 217, 53, 32, 171, 218, 123, 75, 23, 50, 25, 230, 48, 71, 252, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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