Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6d55c9dd1f0fab072db52dde4536bdd3afd27dbed28859c9db26b36688c914e

Tx prefix hash: 57f6a74183da082e845b20e5ac14f5764059583a5678a273aa5cdac914fb6d79
Tx public key: 83e0f42c55bfc9ef65cfb52a63a0fed2cae062b05e215997bf1cfd9a9215f25c
Timestamp: 1736626154 Timestamp [UCT]: 2025-01-11 20:09:14 Age [y:d:h:m:s]: 00:157:22:25:42
Block: 1195247 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112580 RingCT/type: yes/0
Extra: 0183e0f42c55bfc9ef65cfb52a63a0fed2cae062b05e215997bf1cfd9a9215f25c0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13fa2d44dc80de4341fc485f83a0eb8c9776ec47559c59576dc901440e9d4965 0.600000000000 1681836 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": 1195257, "vin": [ { "gen": { "height": 1195247 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13fa2d44dc80de4341fc485f83a0eb8c9776ec47559c59576dc901440e9d4965" } } ], "extra": [ 1, 131, 224, 244, 44, 85, 191, 201, 239, 101, 207, 181, 42, 99, 160, 254, 210, 202, 224, 98, 176, 94, 33, 89, 151, 191, 28, 253, 154, 146, 21, 242, 92, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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