Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b50b4982368786c2bf3c19cc2a9a6e0dafc8109c8d1ab766847e4258d4a49fc0

Tx prefix hash: 31a264c92749b5d4ece0a50b3fc4a50c839665484403adcd8ea10853e1f8f344
Tx public key: 21fdac0d555e54df89a37fd51a8611349e6c03b01841f01a3d2ebe54d23e74e3
Timestamp: 1720751274 Timestamp [UCT]: 2024-07-12 02:27:54 Age [y:d:h:m:s]: 00:267:04:47:45
Block: 1063794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190891 RingCT/type: yes/0
Extra: 0121fdac0d555e54df89a37fd51a8611349e6c03b01841f01a3d2ebe54d23e74e302110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f693b0f26f46228fd95295598fc95e22ac63e23688ebc949d90e12b81eed83c2 0.600000000000 1534311 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": 1063804, "vin": [ { "gen": { "height": 1063794 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f693b0f26f46228fd95295598fc95e22ac63e23688ebc949d90e12b81eed83c2" } } ], "extra": [ 1, 33, 253, 172, 13, 85, 94, 84, 223, 137, 163, 127, 213, 26, 134, 17, 52, 158, 108, 3, 176, 24, 65, 240, 26, 61, 46, 190, 84, 210, 62, 116, 227, 2, 17, 0, 0, 0, 11, 145, 225, 60, 4, 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