Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 759f01b026f49acd1c1328fd240e682f9abfcfa47f0babe652c64e18dd7b4ee3

Tx prefix hash: 96b386c86f5e0a88aa1a82fef68bb2d0ccb229c21a5cac14263ed2939d805e6a
Tx public key: 51d91ce000d3a5afff0e2afeb70e03271a192ddbfecf777ee4afa5cdf8ad6f78
Timestamp: 1740811357 Timestamp [UCT]: 2025-03-01 06:42:37 Age [y:d:h:m:s]: 00:264:18:54:55
Block: 1229624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186994 RingCT/type: yes/0
Extra: 0151d91ce000d3a5afff0e2afeb70e03271a192ddbfecf777ee4afa5cdf8ad6f78021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5de0a25d4d2afee898cc3e03a6236e9dd64fc5af1c1b5cc48bb820d7fc41df03 0.600000000000 1716511 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": 1229634, "vin": [ { "gen": { "height": 1229624 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5de0a25d4d2afee898cc3e03a6236e9dd64fc5af1c1b5cc48bb820d7fc41df03" } } ], "extra": [ 1, 81, 217, 28, 224, 0, 211, 165, 175, 255, 14, 42, 254, 183, 14, 3, 39, 26, 25, 45, 219, 254, 207, 119, 126, 228, 175, 165, 205, 248, 173, 111, 120, 2, 17, 0, 0, 0, 5, 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