Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89d02e5a388ca3dd688db71b9777afb784066481b9556ba70193e5d18f6613e8

Tx prefix hash: a1487830018aeac2c4f1a9d99d509ab1366a04d74f7785f173d89b178261fc0f
Tx public key: 90f7cf69e3c4e3247b60f2c7852d95343e5fc33a51e06e2dd4b7714573133d03
Timestamp: 1713737441 Timestamp [UCT]: 2024-04-21 22:10:41 Age [y:d:h:m:s]: 00:334:23:50:09
Block: 1005626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239490 RingCT/type: yes/0
Extra: 0190f7cf69e3c4e3247b60f2c7852d95343e5fc33a51e06e2dd4b7714573133d030211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4f83b166463f3e79e635e7ab99fb39ec87021c8ae920742ea9a1e884074175d 0.600000000000 1466376 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": 1005636, "vin": [ { "gen": { "height": 1005626 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4f83b166463f3e79e635e7ab99fb39ec87021c8ae920742ea9a1e884074175d" } } ], "extra": [ 1, 144, 247, 207, 105, 227, 196, 227, 36, 123, 96, 242, 199, 133, 45, 149, 52, 62, 95, 195, 58, 81, 224, 110, 45, 212, 183, 113, 69, 115, 19, 61, 3, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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