Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c70d3f87816fe834d514c9400ae76197d5a7c6ce652b863f2b179a31402ec47

Tx prefix hash: 8e194d245a4cf2445ba16504d36ceb943efd95e2ce32ffb7187d41a4af4e326d
Tx public key: e95d3ede83624c15df4179b68655db55f1b2c79bd3b7c99fdf98a6d3e898ad18
Timestamp: 1721987536 Timestamp [UCT]: 2024-07-26 09:52:16 Age [y:d:h:m:s]: 00:213:02:11:00
Block: 1074031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152171 RingCT/type: yes/0
Extra: 01e95d3ede83624c15df4179b68655db55f1b2c79bd3b7c99fdf98a6d3e898ad1802110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ca0d66adf4aee4bc7f345256068877c97916f87e3fa1ce6adf499e0fa53b603 0.600000000000 1546542 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": 1074041, "vin": [ { "gen": { "height": 1074031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ca0d66adf4aee4bc7f345256068877c97916f87e3fa1ce6adf499e0fa53b603" } } ], "extra": [ 1, 233, 93, 62, 222, 131, 98, 76, 21, 223, 65, 121, 182, 134, 85, 219, 85, 241, 178, 199, 155, 211, 183, 201, 159, 223, 152, 166, 211, 232, 152, 173, 24, 2, 17, 0, 0, 0, 11, 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