Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08fbf1e7a55edfba7d4f277c3bfe31eeb3ad5b485b08bb7681dd0f6f50c6762d

Tx prefix hash: e2a978920807a1e6b0eadb61cb0fbe45e0498d63d9b2b09d8eb5c7c0950aba3d
Tx public key: 4f60489783e56959a1e1243595fd7b8319a6918e2221905e4ea6a365da54ef9e
Timestamp: 1702668096 Timestamp [UCT]: 2023-12-15 19:21:36 Age [y:d:h:m:s]: 01:328:21:03:29
Block: 913859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 493908 RingCT/type: yes/0
Extra: 014f60489783e56959a1e1243595fd7b8319a6918e2221905e4ea6a365da54ef9e02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f25811df7602ae0ae6a8967c265c96b447cdd19f12b16a06ea765f148d8f99fb 0.600000000000 1371139 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": 913869, "vin": [ { "gen": { "height": 913859 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f25811df7602ae0ae6a8967c265c96b447cdd19f12b16a06ea765f148d8f99fb" } } ], "extra": [ 1, 79, 96, 72, 151, 131, 229, 105, 89, 161, 225, 36, 53, 149, 253, 123, 131, 25, 166, 145, 142, 34, 33, 144, 94, 78, 166, 163, 101, 218, 84, 239, 158, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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