Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d160258e236d6d486b6d79b0c47226908b4b4dfe4fdb067a747d79d0551ac69f

Tx prefix hash: 381582d8d1f45ad6d6ee94d05b1c2245532c54c25e493a5f39adcb65d2b5da06
Tx public key: f69d949bfdfa94bf288688e98a923387ce89ee0c564d4c996bf8f256e42e0627
Timestamp: 1629384536 Timestamp [UCT]: 2021-08-19 14:48:56 Age [y:d:h:m:s]: 03:135:15:29:27
Block: 317187 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 870496 RingCT/type: yes/0
Extra: 01f69d949bfdfa94bf288688e98a923387ce89ee0c564d4c996bf8f256e42e0627021100000004b75ebe6a000000000000000000

1 output(s) for total of 54.579337997000 dcy

stealth address amount amount idx
00: dd63c7298152649a96812ad6689ee091b5e4ef0f317d741fc2c90c87728f5ad1 54.579337997000 659630 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": 317197, "vin": [ { "gen": { "height": 317187 } } ], "vout": [ { "amount": 54579337997, "target": { "key": "dd63c7298152649a96812ad6689ee091b5e4ef0f317d741fc2c90c87728f5ad1" } } ], "extra": [ 1, 246, 157, 148, 155, 253, 250, 148, 191, 40, 134, 136, 233, 138, 146, 51, 135, 206, 137, 238, 12, 86, 77, 76, 153, 107, 248, 242, 86, 228, 46, 6, 39, 2, 17, 0, 0, 0, 4, 183, 94, 190, 106, 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