Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9c3f16a986fcf3c8f9275497968867006ae18b4c37a33d90c0321008e0e7c16

Tx prefix hash: 6bcd0e282f19af8a77751e1d11d91adcc655544df5ec1a6f5741c85583613347
Tx public key: c9a6f09c4ae039b1275130e5c676f7a1e3a82bb84464bab5b52751fb388dda84
Timestamp: 1729670246 Timestamp [UCT]: 2024-10-23 07:57:26 Age [y:d:h:m:s]: 00:190:01:47:46
Block: 1137696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135646 RingCT/type: yes/0
Extra: 01c9a6f09c4ae039b1275130e5c676f7a1e3a82bb84464bab5b52751fb388dda84021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 791bc8d20fb36c635b80ea7245e7128cf004b4ade614c50d973f9ba7e877e52f 0.600000000000 1621235 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": 1137706, "vin": [ { "gen": { "height": 1137696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "791bc8d20fb36c635b80ea7245e7128cf004b4ade614c50d973f9ba7e877e52f" } } ], "extra": [ 1, 201, 166, 240, 156, 74, 224, 57, 177, 39, 81, 48, 229, 198, 118, 247, 161, 227, 168, 43, 184, 68, 100, 186, 181, 181, 39, 81, 251, 56, 141, 218, 132, 2, 17, 0, 0, 0, 6, 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