Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b9efb3f0a50b3144312754c61504274d9f32c82354f29d9994a0b8683f02eb1

Tx prefix hash: a06911e9a19a256f0a9c658acd41811e28e5ef8d42ea280247f80e9fa61b3eb2
Tx public key: ec0310838fc2e8a885d44a16a4455efb22a3d51ecb8018529069675c46713d18
Timestamp: 1730231843 Timestamp [UCT]: 2024-10-29 19:57:23 Age [y:d:h:m:s]: 00:157:01:45:29
Block: 1142323 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112069 RingCT/type: yes/0
Extra: 01ec0310838fc2e8a885d44a16a4455efb22a3d51ecb8018529069675c46713d18021100000004007f978a000000000000000000

1 output(s) for total of 0.600010000000 dcy

stealth address amount amount idx
00: eda0aca89d0b74f207b975eba335a2a8815d63ff0a28af4bbb7addbcc0a481c5 0.600010000000 1626170 of 0

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": 1142333, "vin": [ { "gen": { "height": 1142323 } } ], "vout": [ { "amount": 600010000, "target": { "key": "eda0aca89d0b74f207b975eba335a2a8815d63ff0a28af4bbb7addbcc0a481c5" } } ], "extra": [ 1, 236, 3, 16, 131, 143, 194, 232, 168, 133, 212, 74, 22, 164, 69, 94, 251, 34, 163, 213, 30, 203, 128, 24, 82, 144, 105, 103, 92, 70, 113, 61, 24, 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