Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d767e244e46a155769f0dbb4d57663d22dc7f9bb4a4f68fecf9d75f18fa224a

Tx prefix hash: cd67447f8bec1a5494d79fbda57f7af4bf0bd66c3fbd4007de566280f2fa9177
Tx public key: e3d345bbb8256c73d0a1cc0e412bda2cfa275c40928c2cb2834ecd33b663b72e
Timestamp: 1709892852 Timestamp [UCT]: 2024-03-08 10:14:12 Age [y:d:h:m:s]: 01:105:06:45:38
Block: 973776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336109 RingCT/type: yes/0
Extra: 01e3d345bbb8256c73d0a1cc0e412bda2cfa275c40928c2cb2834ecd33b663b72e02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a472bedb258cd5a4ab0955fb73e40929b178ca5d386b7e3c0982954a47f092f5 0.600000000000 1433715 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": 973786, "vin": [ { "gen": { "height": 973776 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a472bedb258cd5a4ab0955fb73e40929b178ca5d386b7e3c0982954a47f092f5" } } ], "extra": [ 1, 227, 211, 69, 187, 184, 37, 108, 115, 208, 161, 204, 14, 65, 43, 218, 44, 250, 39, 92, 64, 146, 140, 44, 178, 131, 78, 205, 51, 182, 99, 183, 46, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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