Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be4b44a2a69b0d0fcfe10bfa747efcd53552d275ab0af8584f295cef50a94463

Tx prefix hash: 9446c64fdef70b4152399a477b8b24d4f775d68e868994071ddb70948fa3e70f
Tx public key: c1c28fb495fe5abdaaaadc7d227f39dc70654b691a43819a90a1a421facdb64c
Timestamp: 1706078307 Timestamp [UCT]: 2024-01-24 06:38:27 Age [y:d:h:m:s]: 01:289:03:16:44
Block: 942113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 465461 RingCT/type: yes/0
Extra: 01c1c28fb495fe5abdaaaadc7d227f39dc70654b691a43819a90a1a421facdb64c0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd343b86743c64f4ddc3fcb03b85474706fd45f682ab1ad1a0585c8caef4ecdc 0.600000000000 1400279 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": 942123, "vin": [ { "gen": { "height": 942113 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd343b86743c64f4ddc3fcb03b85474706fd45f682ab1ad1a0585c8caef4ecdc" } } ], "extra": [ 1, 193, 194, 143, 180, 149, 254, 90, 189, 170, 170, 220, 125, 34, 127, 57, 220, 112, 101, 75, 105, 26, 67, 129, 154, 144, 161, 164, 33, 250, 205, 182, 76, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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