Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49a8d5f74b10072c1b1bff894158e09801bd28e24f9646d53b3a69a47ecf3a75

Tx prefix hash: af8c3ad42e9a180cbfc008fda920255082c3197516afd570f5b808f68e6dd4e6
Tx public key: 8b9bfb4c0ea161ccc3170be550b473ca80167265b0fd36c31026d81a6abbd0e1
Timestamp: 1736186619 Timestamp [UCT]: 2025-01-06 18:03:39 Age [y:d:h:m:s]: 00:091:22:21:20
Block: 1191619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65483 RingCT/type: yes/0
Extra: 018b9bfb4c0ea161ccc3170be550b473ca80167265b0fd36c31026d81a6abbd0e1021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cb98d3564be111c1d7e0ae569272492cbdcf64e50c6ba7cc8320dbdbf25e148 0.600000000000 1678160 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": 1191629, "vin": [ { "gen": { "height": 1191619 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cb98d3564be111c1d7e0ae569272492cbdcf64e50c6ba7cc8320dbdbf25e148" } } ], "extra": [ 1, 139, 155, 251, 76, 14, 161, 97, 204, 195, 23, 11, 229, 80, 180, 115, 202, 128, 22, 114, 101, 176, 253, 54, 195, 16, 38, 216, 26, 106, 187, 208, 225, 2, 17, 0, 0, 0, 8, 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