Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd15264d2cb58cf06b72aa95df9a41c41d04ffa7199618c705d5e0486a5958b4

Tx prefix hash: 621753f2d5d3f131623b20b79e45c988786b55469dc743067a445bf648814728
Tx public key: 154628ae939005e9884e5f19df72f2b7d35991f635061e814ca2d7a5fdf5f5f7
Timestamp: 1699453666 Timestamp [UCT]: 2023-11-08 14:27:46 Age [y:d:h:m:s]: 01:142:04:11:08
Block: 887219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362799 RingCT/type: yes/0
Extra: 01154628ae939005e9884e5f19df72f2b7d35991f635061e814ca2d7a5fdf5f5f7021100000004faf35c9c000000000000000000

1 output(s) for total of 0.705149678000 dcy

stealth address amount amount idx
00: 9c0d61be890ed3a0adc6a166bee3d6f367572b0e3fb4a908e240ca9e513cd84c 0.705149678000 1343086 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": 887229, "vin": [ { "gen": { "height": 887219 } } ], "vout": [ { "amount": 705149678, "target": { "key": "9c0d61be890ed3a0adc6a166bee3d6f367572b0e3fb4a908e240ca9e513cd84c" } } ], "extra": [ 1, 21, 70, 40, 174, 147, 144, 5, 233, 136, 78, 95, 25, 223, 114, 242, 183, 211, 89, 145, 246, 53, 6, 30, 129, 76, 162, 215, 165, 253, 245, 245, 247, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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