Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a388ef99950e2b12488e812905023d9807dcd9eadb435904395d048eeefd947

Tx prefix hash: b6267be760e6d4c2b3188454e1b0b8805e00b1a4700a7754748bfa9bcd3041a4
Tx public key: 8cc1bdcbb3ea4a53d0e3f131a7d5685b2edf21451ecb0dfa933899ccb97da411
Timestamp: 1731097143 Timestamp [UCT]: 2024-11-08 20:19:03 Age [y:d:h:m:s]: 00:131:10:33:27
Block: 1149479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93766 RingCT/type: yes/0
Extra: 018cc1bdcbb3ea4a53d0e3f131a7d5685b2edf21451ecb0dfa933899ccb97da411021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9226ea55d5f2b018a416d4878c1006d69b83018bd045e9dd4c044de627522786 0.600000000000 1634568 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": 1149489, "vin": [ { "gen": { "height": 1149479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9226ea55d5f2b018a416d4878c1006d69b83018bd045e9dd4c044de627522786" } } ], "extra": [ 1, 140, 193, 189, 203, 179, 234, 74, 83, 208, 227, 241, 49, 167, 213, 104, 91, 46, 223, 33, 69, 30, 203, 13, 250, 147, 56, 153, 204, 185, 125, 164, 17, 2, 17, 0, 0, 0, 6, 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