Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 400eb99617cab8fe7350d03c211eb457fd863d5dd103fba7e323238b3c28364f

Tx prefix hash: a1c0f594460d5f66f1858e2d45c0fb796f39d546f33b2a4ff2ea6690a9543789
Tx public key: c984c950d3fb63755b0fae2c34a8f451ced5d98ca6bdc8f8088bbf7a33e9b762
Timestamp: 1727234498 Timestamp [UCT]: 2024-09-25 03:21:38 Age [y:d:h:m:s]: 01:045:20:25:42
Block: 1117531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291172 RingCT/type: yes/0
Extra: 01c984c950d3fb63755b0fae2c34a8f451ced5d98ca6bdc8f8088bbf7a33e9b76202110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38eb6dab3bd92b18b2ebf0efd92ec78c30a9995be0a4fd6aa32465df1f0bedd4 0.600000000000 1598404 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": 1117541, "vin": [ { "gen": { "height": 1117531 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38eb6dab3bd92b18b2ebf0efd92ec78c30a9995be0a4fd6aa32465df1f0bedd4" } } ], "extra": [ 1, 201, 132, 201, 80, 211, 251, 99, 117, 91, 15, 174, 44, 52, 168, 244, 81, 206, 213, 217, 140, 166, 189, 200, 248, 8, 139, 191, 122, 51, 233, 183, 98, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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