Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf716677d438e46c91970f674462d0e8824db274ad0f92c9e39d58d243e46d77

Tx prefix hash: bfff1f7658d11e69c0c6318d978f1efc1235891e5c9a54182b4dd9442b9b833f
Tx public key: 0ad4c35ea70fdeb3509489eb8dfddbd4737a612aef1d87eec13fe28a505dca8c
Timestamp: 1731647997 Timestamp [UCT]: 2024-11-15 05:19:57 Age [y:d:h:m:s]: 00:009:01:25:00
Block: 1154021 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6490 RingCT/type: yes/0
Extra: 010ad4c35ea70fdeb3509489eb8dfddbd4737a612aef1d87eec13fe28a505dca8c021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49f4ec3d298e408ffca55e3181f2745573ba8a320ed70ef9316c280a558e6126 0.600000000000 1639632 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": 1154031, "vin": [ { "gen": { "height": 1154021 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49f4ec3d298e408ffca55e3181f2745573ba8a320ed70ef9316c280a558e6126" } } ], "extra": [ 1, 10, 212, 195, 94, 167, 15, 222, 179, 80, 148, 137, 235, 141, 253, 219, 212, 115, 122, 97, 42, 239, 29, 135, 238, 193, 63, 226, 138, 80, 93, 202, 140, 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