Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5efb6a1846e44085768a37324a82736ed627c83d1a44622a8801c8db30aad4bc

Tx prefix hash: 7716e3e675e85daf3db4edf86a9634a0db240b1481d28c115ff1645a3c8d2657
Tx public key: 495fb6dcae6952c83e34b1cd4914a6a1fdd33dc4c1b37065e034a36bfdc28881
Timestamp: 1725139052 Timestamp [UCT]: 2024-08-31 21:17:32 Age [y:d:h:m:s]: 01:060:14:48:39
Block: 1100152 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301763 RingCT/type: yes/0
Extra: 01495fb6dcae6952c83e34b1cd4914a6a1fdd33dc4c1b37065e034a36bfdc2888102110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89c77211b09ffe16de72e08002b7a1e4ace2fce30311202654a9fdc4851df3b5 0.600000000000 1576125 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": 1100162, "vin": [ { "gen": { "height": 1100152 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89c77211b09ffe16de72e08002b7a1e4ace2fce30311202654a9fdc4851df3b5" } } ], "extra": [ 1, 73, 95, 182, 220, 174, 105, 82, 200, 62, 52, 177, 205, 73, 20, 166, 161, 253, 211, 61, 196, 193, 179, 112, 101, 224, 52, 163, 107, 253, 194, 136, 129, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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