Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d43353e0936eac1de3ec8cc771c25a540dce63161bf7a925d400cc7dc5b0ccf

Tx prefix hash: 4c11b0d013d55cef863d1ca0981b839b3b4184a03ee8a3b822a2de6a517e06a5
Tx public key: c39e1e38d16f77e0e1b6b5e26a86ef7731e4b59218b247b7d141859c32051f3d
Timestamp: 1681477817 Timestamp [UCT]: 2023-04-14 13:10:17 Age [y:d:h:m:s]: 01:357:14:16:16
Block: 738431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 516847 RingCT/type: yes/0
Extra: 01c39e1e38d16f77e0e1b6b5e26a86ef7731e4b59218b247b7d141859c32051f3d0211000000035029cbac000000000000000000

1 output(s) for total of 2.194177614000 dcy

stealth address amount amount idx
00: 5dd3eeeff4f4d3821c73bf16e821d59e2beab718e06c02827770efa3039f1a1d 2.194177614000 1185116 of 0

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": 738441, "vin": [ { "gen": { "height": 738431 } } ], "vout": [ { "amount": 2194177614, "target": { "key": "5dd3eeeff4f4d3821c73bf16e821d59e2beab718e06c02827770efa3039f1a1d" } } ], "extra": [ 1, 195, 158, 30, 56, 209, 111, 119, 224, 225, 182, 181, 226, 106, 134, 239, 119, 49, 228, 181, 146, 24, 178, 71, 183, 209, 65, 133, 156, 50, 5, 31, 61, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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