Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca14818541353f1d4c9d3ee655e19f20832ee29991fdaeb4632def4ae3092b08

Tx prefix hash: 009f323f6342c8ba3f58518a153636234055917f80ab19c1f40865df291c0f33
Tx public key: fe55ff3c93cd1e0f8e2e6bbe429e8a477c050e8c84298fa91bafc6e8af7cb9dc
Timestamp: 1674030111 Timestamp [UCT]: 2023-01-18 08:21:51 Age [y:d:h:m:s]: 02:305:15:56:15
Block: 677306 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 737859 RingCT/type: yes/0
Extra: 01fe55ff3c93cd1e0f8e2e6bbe429e8a477c050e8c84298fa91bafc6e8af7cb9dc021100000004e6d27f9c000000000000000000

1 output(s) for total of 3.497872744000 dcy

stealth address amount amount idx
00: 5f0b8fd57c66f6d6bbfcd8be8146a5303c016b74ac085ec8ffb40253fb7e5d31 3.497872744000 1119079 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": 677316, "vin": [ { "gen": { "height": 677306 } } ], "vout": [ { "amount": 3497872744, "target": { "key": "5f0b8fd57c66f6d6bbfcd8be8146a5303c016b74ac085ec8ffb40253fb7e5d31" } } ], "extra": [ 1, 254, 85, 255, 60, 147, 205, 30, 15, 142, 46, 107, 190, 66, 158, 138, 71, 124, 5, 14, 140, 132, 41, 143, 169, 27, 175, 198, 232, 175, 124, 185, 220, 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