Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb7eb2e5f351615060da9a72532f5e00c764c1de140cf58ddaf3059960fec000

Tx prefix hash: 5f9c1607def1caacd29a3f927c5a1e1d211d7dc64d97e41b02f594cdc03894ee
Tx public key: 871b6a69d4f924772031d8953f0560b40e5fae9a06ff81e9c9c6c816d260f49a
Timestamp: 1696026212 Timestamp [UCT]: 2023-09-29 22:23:32 Age [y:d:h:m:s]: 01:237:11:30:41
Block: 859006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 430817 RingCT/type: yes/0
Extra: 01871b6a69d4f924772031d8953f0560b40e5fae9a06ff81e9c9c6c816d260f49a0211000000024b8f5122000000000000000000

1 output(s) for total of 0.874493478000 dcy

stealth address amount amount idx
00: 701ef3326c40297a2440fe4b72e7a8c3d44747391a254efd69b4b8db10d5857e 0.874493478000 1313212 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": 859016, "vin": [ { "gen": { "height": 859006 } } ], "vout": [ { "amount": 874493478, "target": { "key": "701ef3326c40297a2440fe4b72e7a8c3d44747391a254efd69b4b8db10d5857e" } } ], "extra": [ 1, 135, 27, 106, 105, 212, 249, 36, 119, 32, 49, 216, 149, 63, 5, 96, 180, 14, 95, 174, 154, 6, 255, 129, 233, 201, 198, 200, 22, 210, 96, 244, 154, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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