Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a8a15641df15d4746d72608ba56e3df65588d9549159cd9cbaf7dcaa698a1d3

Tx prefix hash: fe00e282db6496c80be14f8f3f4060f7095c2e053c0a61a6c4a446023ebe69a3
Tx public key: 3b2cf4fd8e40e2fef0726b06841eae52bcde84d9a0feadc61b317edf16bbb7a2
Timestamp: 1738149506 Timestamp [UCT]: 2025-01-29 11:18:26 Age [y:d:h:m:s]: 00:296:05:37:49
Block: 1207599 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209480 RingCT/type: yes/0
Extra: 013b2cf4fd8e40e2fef0726b06841eae52bcde84d9a0feadc61b317edf16bbb7a20211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e8fa207fc415a0c8046ddb9d958d7d3270823aa969d3ee5039726a689ef5e1e 0.600000000000 1694324 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": 1207609, "vin": [ { "gen": { "height": 1207599 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e8fa207fc415a0c8046ddb9d958d7d3270823aa969d3ee5039726a689ef5e1e" } } ], "extra": [ 1, 59, 44, 244, 253, 142, 64, 226, 254, 240, 114, 107, 6, 132, 30, 174, 82, 188, 222, 132, 217, 160, 254, 173, 198, 27, 49, 126, 223, 22, 187, 183, 162, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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