Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02a34b88b88acbef8c309cec3f97b93e3cd25fdc9bd98077ec5cb28f4cc86c94

Tx prefix hash: 496e802358bb1bedd55e99dc5dbf544268130dff1e5d4e92891933dd132be6e6
Tx public key: 4638f15adca61e61c7aac7a5b6f82453277657cc66faa874d8d609b779197d62
Timestamp: 1729240410 Timestamp [UCT]: 2024-10-18 08:33:30 Age [y:d:h:m:s]: 00:036:23:37:42
Block: 1134172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26386 RingCT/type: yes/0
Extra: 014638f15adca61e61c7aac7a5b6f82453277657cc66faa874d8d609b779197d6202110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e293d0f172f0bae999da6e65630a3ab1c17d69e0da47974fcf8ce04a23a511aa 0.600000000000 1617433 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": 1134182, "vin": [ { "gen": { "height": 1134172 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e293d0f172f0bae999da6e65630a3ab1c17d69e0da47974fcf8ce04a23a511aa" } } ], "extra": [ 1, 70, 56, 241, 90, 220, 166, 30, 97, 199, 170, 199, 165, 182, 248, 36, 83, 39, 118, 87, 204, 102, 250, 168, 116, 216, 214, 9, 183, 121, 25, 125, 98, 2, 17, 0, 0, 0, 10, 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