Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 896854282375603c3dda204ab78993a112c4e8ee2e6c28b29a13beac8808eefc

Tx prefix hash: 1e932a0697e6e1d7177316643f47972a9d29b0fe65c0ba823a5b356b58d214e6
Tx public key: c77dce479ed4a91caaaf7aa479f53ca2d610b4094d0fece5dd224f95d6dd1227
Timestamp: 1734928129 Timestamp [UCT]: 2024-12-23 04:28:49 Age [y:d:h:m:s]: 00:175:05:29:35
Block: 1181228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124934 RingCT/type: yes/0
Extra: 01c77dce479ed4a91caaaf7aa479f53ca2d610b4094d0fece5dd224f95d6dd1227021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7795de30bb2eb8a610c36e07b8a94091c4224e0e2ec8136b2a49b430325607a5 0.600000000000 1667645 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": 1181238, "vin": [ { "gen": { "height": 1181228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7795de30bb2eb8a610c36e07b8a94091c4224e0e2ec8136b2a49b430325607a5" } } ], "extra": [ 1, 199, 125, 206, 71, 158, 212, 169, 28, 170, 175, 122, 164, 121, 245, 60, 162, 214, 16, 180, 9, 77, 15, 236, 229, 221, 34, 79, 149, 214, 221, 18, 39, 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