Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f35a467e12543ba255d0c62a606f65ab6b8ff9ddda9ee28b9f206fafd7b9a47

Tx prefix hash: 773e9b3c916c0112b9582e4b5e2f8cd89e4859e3ee79aabe811af84438d53051
Tx public key: 3d6169d0e5fe2f358d7bf203dcbc80dae1d650d1f54f4b83516bd7633fe02311
Timestamp: 1732064018 Timestamp [UCT]: 2024-11-20 00:53:38 Age [y:d:h:m:s]: 00:210:05:57:18
Block: 1157483 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150004 RingCT/type: yes/0
Extra: 013d6169d0e5fe2f358d7bf203dcbc80dae1d650d1f54f4b83516bd7633fe023110211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dda1c55a83fad79bf96c2f22238e6d6eec70d49ae2841d740af364ff4d295969 0.600000000000 1643106 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": 1157493, "vin": [ { "gen": { "height": 1157483 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dda1c55a83fad79bf96c2f22238e6d6eec70d49ae2841d740af364ff4d295969" } } ], "extra": [ 1, 61, 97, 105, 208, 229, 254, 47, 53, 141, 123, 242, 3, 220, 188, 128, 218, 225, 214, 80, 209, 245, 79, 75, 131, 81, 107, 215, 99, 63, 224, 35, 17, 2, 17, 0, 0, 0, 9, 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