Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16ef5168d3f9c7bf6f13a86b73e59770323efb248ea72f47338b7f0720ec635b

Tx prefix hash: 5c92d6cca1f277a3a830d4a83f029eb580442fdf389ac8d0f5e8b001b7dd5373
Tx public key: bbbe69648b877bea7f34d41681242690e0d020f63f503a90d8378bfb00e5d8b0
Timestamp: 1736584880 Timestamp [UCT]: 2025-01-11 08:41:20 Age [y:d:h:m:s]: 00:080:01:32:31
Block: 1194914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56989 RingCT/type: yes/0
Extra: 01bbbe69648b877bea7f34d41681242690e0d020f63f503a90d8378bfb00e5d8b0021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5771b9b58565d42fea9f228c8cff6bb690fe0aea43d49804e9a62954bb73ba8 0.600000000000 1681493 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": 1194924, "vin": [ { "gen": { "height": 1194914 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5771b9b58565d42fea9f228c8cff6bb690fe0aea43d49804e9a62954bb73ba8" } } ], "extra": [ 1, 187, 190, 105, 100, 139, 135, 123, 234, 127, 52, 212, 22, 129, 36, 38, 144, 224, 208, 32, 246, 63, 80, 58, 144, 216, 55, 139, 251, 0, 229, 216, 176, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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