Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc346e27ef9180f885b5d7620169383f243053ee1f914b518836f5021c68a8f4

Tx prefix hash: f1f80a0bd5f74ab0d095d1c03404c21c295e2d0edbb3af7c383c68a374f48167
Tx public key: 286e89cbdb673c30f3d372354ce5a1da7a3037bab9a952ff964545a75077f2a8
Timestamp: 1702339544 Timestamp [UCT]: 2023-12-12 00:05:44 Age [y:d:h:m:s]: 01:189:23:48:27
Block: 911151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396825 RingCT/type: yes/0
Extra: 01286e89cbdb673c30f3d372354ce5a1da7a3037bab9a952ff964545a75077f2a8021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a47bf80a4884dbb7ba0da59b0fcbe13771fe1a638ea14e03d517068d8d2c7df 0.600000000000 1368332 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": 911161, "vin": [ { "gen": { "height": 911151 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a47bf80a4884dbb7ba0da59b0fcbe13771fe1a638ea14e03d517068d8d2c7df" } } ], "extra": [ 1, 40, 110, 137, 203, 219, 103, 60, 48, 243, 211, 114, 53, 76, 229, 161, 218, 122, 48, 55, 186, 185, 169, 82, 255, 150, 69, 69, 167, 80, 119, 242, 168, 2, 17, 0, 0, 0, 4, 230, 210, 127, 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