Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1dc5715ec43e7c66cd340fabdd6155e9c7ef739dfcabc609acc3b45e9e1f5f4

Tx prefix hash: 50b622ac5e97d94f1181fa95e4a1ee046fde904b1984de331eb2d6d741a2721b
Tx public key: 8170201cb39237966d6528dde60414fde6f441dc57f922f7b45c9b2d732e77e1
Timestamp: 1719168336 Timestamp [UCT]: 2024-06-23 18:45:36 Age [y:d:h:m:s]: 00:285:01:00:37
Block: 1050642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203691 RingCT/type: yes/0
Extra: 018170201cb39237966d6528dde60414fde6f441dc57f922f7b45c9b2d732e77e102110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a90a78ae32107132c977aaaf92c90a233e5214bab5335fb33a6d93ea0e8ac3a1 0.600000000000 1520817 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": 1050652, "vin": [ { "gen": { "height": 1050642 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a90a78ae32107132c977aaaf92c90a233e5214bab5335fb33a6d93ea0e8ac3a1" } } ], "extra": [ 1, 129, 112, 32, 28, 179, 146, 55, 150, 109, 101, 40, 221, 230, 4, 20, 253, 230, 244, 65, 220, 87, 249, 34, 247, 180, 92, 155, 45, 115, 46, 119, 225, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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