Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 635fb127599994677c29fda95c5bdf5238dea2eaa68a5c57500ee2ea5cde6007

Tx prefix hash: 1120367f30a8a9fbe50afd795d03fada691a564b8a594832c821acede13f5668
Tx public key: 5cf5c19cd7a7f0d5d90d302689dba972c5ca33aa2ed3227d4df511a11cae684f
Timestamp: 1736491402 Timestamp [UCT]: 2025-01-10 06:43:22 Age [y:d:h:m:s]: 00:156:05:36:49
Block: 1194142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111383 RingCT/type: yes/0
Extra: 015cf5c19cd7a7f0d5d90d302689dba972c5ca33aa2ed3227d4df511a11cae684f021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6488cdefac5ed660bfcb37a27c65d55a6334ae32a7e91e95c88fdcf34340ffd6 0.600000000000 1680709 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": 1194152, "vin": [ { "gen": { "height": 1194142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6488cdefac5ed660bfcb37a27c65d55a6334ae32a7e91e95c88fdcf34340ffd6" } } ], "extra": [ 1, 92, 245, 193, 156, 215, 167, 240, 213, 217, 13, 48, 38, 137, 219, 169, 114, 197, 202, 51, 170, 46, 211, 34, 125, 77, 245, 17, 161, 28, 174, 104, 79, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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