Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e0272ea4950488c36eec28a0e44d1fe38c128695c71a96ba7cfa25a71c98d0b

Tx prefix hash: fff4b5395699f33ce927b1a859a9e83aeb86a5bc2da3773cbcb67ea14d7a5bc0
Tx public key: 2cad29653fea4cf58329dec1a7ed4e6e172f4a8bcd2ceafd657106d826c1e75d
Timestamp: 1695492641 Timestamp [UCT]: 2023-09-23 18:10:41 Age [y:d:h:m:s]: 01:154:00:52:00
Block: 854568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371127 RingCT/type: yes/0
Extra: 012cad29653fea4cf58329dec1a7ed4e6e172f4a8bcd2ceafd657106d826c1e75d021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.904610278000 dcy

stealth address amount amount idx
00: af422a5a6c776573f674ff1a554473a8675d91b7bfb7a0f42ad8bc31882dc674 0.904610278000 1308550 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": 854578, "vin": [ { "gen": { "height": 854568 } } ], "vout": [ { "amount": 904610278, "target": { "key": "af422a5a6c776573f674ff1a554473a8675d91b7bfb7a0f42ad8bc31882dc674" } } ], "extra": [ 1, 44, 173, 41, 101, 63, 234, 76, 245, 131, 41, 222, 193, 167, 237, 78, 110, 23, 47, 74, 139, 205, 44, 234, 253, 101, 113, 6, 216, 38, 193, 231, 93, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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