Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f377d9a2098c8ab1ace890f0d94bc7939b20a8b55ab9e634541f5e66c60e3885

Tx prefix hash: 15832ad19bfeefc78e9234bbd820b8ef83b1b9906cf8a7cf8b08236ca492cf6e
Tx public key: 37055fe3f80e9ef339f52f0ba98b7e09b3c3c572d317c4a304c354fa1edad2e5
Timestamp: 1728938103 Timestamp [UCT]: 2024-10-14 20:35:03 Age [y:d:h:m:s]: 00:249:14:45:34
Block: 1131659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178061 RingCT/type: yes/0
Extra: 0137055fe3f80e9ef339f52f0ba98b7e09b3c3c572d317c4a304c354fa1edad2e5021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ee9b804be5832b923aff2d23edee41baed9eaff3986ac8f2dc53831e4930289 0.600000000000 1614562 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": 1131669, "vin": [ { "gen": { "height": 1131659 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ee9b804be5832b923aff2d23edee41baed9eaff3986ac8f2dc53831e4930289" } } ], "extra": [ 1, 55, 5, 95, 227, 248, 14, 158, 243, 57, 245, 47, 11, 169, 139, 126, 9, 179, 195, 197, 114, 211, 23, 196, 163, 4, 195, 84, 250, 30, 218, 210, 229, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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