Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 047d161aadf70e61cff565561340b240b0241a74950f270773a9986742736655

Tx prefix hash: dc4f806c7d13bc239e46e899c11a06df47ae1b77df84faeb36e27e93e6e62c01
Tx public key: f14ed878e3014a93d29b491fc7593941dd1c71248323f9a1e11c78df8f34e9e5
Timestamp: 1709278468 Timestamp [UCT]: 2024-03-01 07:34:28 Age [y:d:h:m:s]: 01:266:23:23:45
Block: 968677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 449547 RingCT/type: yes/0
Extra: 01f14ed878e3014a93d29b491fc7593941dd1c71248323f9a1e11c78df8f34e9e502110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9569f266b66f3f5fe8f8376733d4fed0658d2ea083d5d76b46a4edb8a15bf03 0.600000000000 1428494 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": 968687, "vin": [ { "gen": { "height": 968677 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9569f266b66f3f5fe8f8376733d4fed0658d2ea083d5d76b46a4edb8a15bf03" } } ], "extra": [ 1, 241, 78, 216, 120, 227, 1, 74, 147, 210, 155, 73, 31, 199, 89, 57, 65, 221, 28, 113, 36, 131, 35, 249, 161, 225, 28, 120, 223, 143, 52, 233, 229, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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