Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 153af229a72be250e9eb807dc50a936e65e1c7a74127710a09776d40c19d79ca

Tx prefix hash: 932903595b20d6b2f3eab3c46587638cbf6f5b5e39b79839ddbff1f4cc8fe877
Tx public key: 4f2d50d412493a266b7d1104b10e26f3837cbdae4253843694abc9287e0f8b27
Timestamp: 1736676136 Timestamp [UCT]: 2025-01-12 10:02:16 Age [y:d:h:m:s]: 00:154:12:30:39
Block: 1195668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110163 RingCT/type: yes/0
Extra: 014f2d50d412493a266b7d1104b10e26f3837cbdae4253843694abc9287e0f8b270211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 252850166978c678522fab2892afe33361410b8f2e2e6c2e824768e67789c9aa 0.600000000000 1682259 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": 1195678, "vin": [ { "gen": { "height": 1195668 } } ], "vout": [ { "amount": 600000000, "target": { "key": "252850166978c678522fab2892afe33361410b8f2e2e6c2e824768e67789c9aa" } } ], "extra": [ 1, 79, 45, 80, 212, 18, 73, 58, 38, 107, 125, 17, 4, 177, 14, 38, 243, 131, 124, 189, 174, 66, 83, 132, 54, 148, 171, 201, 40, 126, 15, 139, 39, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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