Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd1a0aed82a35c99ca0cdc72feafd4e80ec83fb904c555fdce474052c2ddf73f

Tx prefix hash: d9572a80c56af1db04cb35b98dea74708e52e0402b304730c1aef759ca16f3ea
Tx public key: 6008ac0c2ae57b5811038f71e10d6c260bf2c2a4eadf4ab7d2a420c2ae852c16
Timestamp: 1709363661 Timestamp [UCT]: 2024-03-02 07:14:21 Age [y:d:h:m:s]: 01:035:05:45:02
Block: 969382 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286179 RingCT/type: yes/0
Extra: 016008ac0c2ae57b5811038f71e10d6c260bf2c2a4eadf4ab7d2a420c2ae852c1602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be4b39a1be4855a187cd1e96c4f1d37a5a2ed3e48372ccc6a6c8ccd8ccc7087b 0.600000000000 1429211 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": 969392, "vin": [ { "gen": { "height": 969382 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be4b39a1be4855a187cd1e96c4f1d37a5a2ed3e48372ccc6a6c8ccd8ccc7087b" } } ], "extra": [ 1, 96, 8, 172, 12, 42, 229, 123, 88, 17, 3, 143, 113, 225, 13, 108, 38, 11, 242, 194, 164, 234, 223, 74, 183, 210, 164, 32, 194, 174, 133, 44, 22, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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