Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47ff18ee382cdc609157f0c4c4e475e29a17975832bde14f6e3e73eabd835f6c

Tx prefix hash: e3a3aecaf64e091c2694e6debac91ad18cf31f0f1c5b4ee881154d3ad9e04469
Tx public key: 80b1e925cec4b3f32a54d826b009b16665f57bf7831fbc4213a1d65f3a6df7de
Timestamp: 1697333465 Timestamp [UCT]: 2023-10-15 01:31:05 Age [y:d:h:m:s]: 01:157:18:46:25
Block: 869838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373810 RingCT/type: yes/0
Extra: 0180b1e925cec4b3f32a54d826b009b16665f57bf7831fbc4213a1d65f3a6df7de02110000000833af99f4000000000000000000

1 output(s) for total of 0.805129328000 dcy

stealth address amount amount idx
00: 13cb37976df9229c1a556ed3f826da5b8fb52fc8884f622f8e3cc96a482a6b40 0.805129328000 1324699 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": 869848, "vin": [ { "gen": { "height": 869838 } } ], "vout": [ { "amount": 805129328, "target": { "key": "13cb37976df9229c1a556ed3f826da5b8fb52fc8884f622f8e3cc96a482a6b40" } } ], "extra": [ 1, 128, 177, 233, 37, 206, 196, 179, 243, 42, 84, 216, 38, 176, 9, 177, 102, 101, 245, 123, 247, 131, 31, 188, 66, 19, 161, 214, 95, 58, 109, 247, 222, 2, 17, 0, 0, 0, 8, 51, 175, 153, 244, 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