Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24fc549d9ab99637260113def4cb5da88a474033598f490398f9fad3344f5b27

Tx prefix hash: d902ed7161bf0e42b932fc3a35b0ac853a84ca86f28561382953b52133b3ed4b
Tx public key: 1a8d5cc075b50ec80276360656ab9fa79dfab3172e4934c5b7715476f43e1b85
Timestamp: 1717648515 Timestamp [UCT]: 2024-06-06 04:35:15 Age [y:d:h:m:s]: 00:284:08:10:00
Block: 1038061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203217 RingCT/type: yes/0
Extra: 011a8d5cc075b50ec80276360656ab9fa79dfab3172e4934c5b7715476f43e1b8502110000000d7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ae909d4a8f2b6dbe306b8d54aec7b7f31ed7d781fad2325584e2568a276fe45 0.600000000000 1506620 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": 1038071, "vin": [ { "gen": { "height": 1038061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ae909d4a8f2b6dbe306b8d54aec7b7f31ed7d781fad2325584e2568a276fe45" } } ], "extra": [ 1, 26, 141, 92, 192, 117, 181, 14, 200, 2, 118, 54, 6, 86, 171, 159, 167, 157, 250, 179, 23, 46, 73, 52, 197, 183, 113, 84, 118, 244, 62, 27, 133, 2, 17, 0, 0, 0, 13, 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